Micron Document

Propagation node
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Propagation nodes store and forward LXMF messages to nodes that are not directly reachable when a message is sent.

It enables asynchronous messaging between peers. Messages stay encrypted the whole time, and only reveal the sender to the recipient.cite-ref-0-1-0[1]

Propagation nodes will, by default, peer with each other and synchronize messages over time, automatically creating an encrypted, distributed message store. Users can retrieve their messages from any available propagation node.cite-ref-0-1-1[1]

Note: LXMF's propagation nodes are not the same as Reticulum's transport nodes; propagation nodes provide optional asynchronous messaging features to LXMF while transport nodes enable multi-hop routing at the Reticulum Protocol level.cite-ref-0-1-2[1]



References

cite-note-0-11. Linux in a Bit. "The Reticulum Network and How it Works". Linux in a Bit's Stuff.

Reticulum concepts

AnnounceBlackholeBufferChannelDestinationDiscoveryIdentityInstanceInterfaceInterface Access Code (IFAC) • LinkNetwork identityNodePacketPath • Propagation node • ResourceStampTransport node

Propagation node